Upgrading and installing are almost identical, except that upgrading requires connection to your existing database so that the installer can automatically run the DB Upgrader utility during the process.
1. Finish all tasks in Preparing all servers and workstations and review the System requirements.
2. (upgrades) Finish all tasks in Preparing to upgrade.
3. (upgrades) Any iMIS Desktop View navigation item that uses the Open the link in a new window option needs to be deselected prior to the upgrade. Otherwise, the site administrator will need to remove the navigation item and recreate it.
4. (upgrades) Have all users log out of iMIS.
5. (upgrades) Uninstall iMIS if any of the following have been changed manually since the last upgrade:
□ Database name
□ Database server name or IP
□ Virtual directory name
□ Machine name
□ Path to iMISPublic or iMIS
6. (upgrades) If you have Analytics installed, remove it to avoid triggering reinstallation and reconfiguration of a new analytics database and analysis server:
□
Back up your Analytics files, such as
move
"C:\Program Files\ASI\iMIS\Analytics"
"C:\Program Files\ASI\iMIS\Analytics.bak"
□ Select Control Panel > Programs and Features.
□ Open (double-click) iMIS to access the installer options.
□ Select Modify, expand Optional Components, and deselect iMIS Analytics.
□ Select Next as needed and Finish, then proceed with the upgrade.
7. On your application server host, temporarily disable tools and settings that might interfere with installation.
□ Disable anti-virus software.
□ Turn off UAC (User Account Control) settings:
■ From your computer’s Control Panel, select User Accounts.
■ Locate the User Account Settings and turn the setting off or move the slide bar to Never notify and click OK.
8. Run the product setup.exe.
9. Welcome page: Click Next.
10. Select installation type page: Pick the type and click Next.
Complete installs a single iMIS appserver, with these results:
□ All core components are installed, but no optional applications
□ The appserver supports all user classes and views (see Types of iMIS licenses and views)
□ All pre-configured installers are available for download from the appserver
Custom installs everything covered in Complete and lets you add items:
□ multiple iMIS application servers, choosing the specific iMIS applications and optional components that you want on each host
□ iMIS Analytics, even in a single appserver environment
Tip: The appserver from which users download the Desktop installer is the one to which the installed Desktop will connect; therefore, to balance loads across the organization, put pre-configured installers on each appserver they'll use.
11. Select destination location page: Click Next to accept the default installation path (recommended).
12. Specify database connection page: Enter the connection and click Next.
□ In the SQL Server Name list, select a SQL Server instance or enter the name manually.
□ Next, choose whether to Create new database or Upgrade an existing database. Changing this mode enables different fields.
□ In Database Name (case-sensitive), enter the name of your iMIS database. Ensure that the name is valid for your SQL Server configuration.
Caution! The iMIS database name must begin with a letter. Do not use (local), and do not use special characters in the name.
□ (new databases) For greatest security, enable the checkbox to Use separate (sa) credentials when creating new database. See Accounts for database access.
■ In the fields on the right, specify a system administrator account, which the installer will use only temporarily.
■ In the fields to the left, specify values for a new, standalone user account to be created by the sysadmin account. These values will be used in your config file for enabling database access (db_owner).
□ (upgrades) Under User Name, enter the sysadmin login for the SQL Server instance that is hosting the iMIS database.
□ In Password, specify the password for the account(s) you entered. If blank, the upgrade will fail.
Caution! Special characters in the password can disrupt command-line processing, so use only alphanumeric characters and ! # @, with no spaces. You may use hyphens and underscores after the first character, but avoid all other punctuation and symbols.
13. (optional) Analytics: Specify the connection information for the Analytics data warehouse and analysis database.
Note: The Integration Services packages used by Analytics require the database server host to have a default instance of SQL Server installed on it, which must be installed with SQL Server 2005 Integration Services (SSIS).
14. (upgrades) Review any warnings that appear and take the recommended action.
15. Specify iMIS configuration page: Enter any virtual roots, SMTP server, and other information, and click Next.
□ In iMIS application root, select a root, which affects the final URL:
■ Default website: Sets iMIS as the default website for your domain, which will display whichever iMIS site you specify as being the default in Content Management.
Caution! This option overrides any other website that you previously set as the default.
■ Virtual root: (required for multiple instances) Sets the root below which all of your iMIS sites will appear on your domain.
□ In Public website virtual root, leave the default value of iMISpublic unless you have a need to change it. This value forms part of the final URL.
□ In SMTP server name, specify the domain name of your SMTP server.
Caution! An invalid domain name will cause several email notification features to fail until you perform troubleshooting steps (see " Email output or event invites not sent or received).
□ Write down the URLs shown for all virtual roots: you will need these later.
□ Accept the Publishing Server Code default; however, if you later install additional publishing services, set them to different letters.
The Publishing Server Code associates the physical publishing service (running on a webserver) with the specific Publish Server record in the database that configures it; choose different letters as needed to avoid colliding with the mapping of other installers. If the wizard detects that the path for the code you selected differs from your install location, it prompts you change either the install directory or the publishing service code.
□ Accept the Indexing Catalog Name default, unless you need to store CM search metadata in an existing Index Server catalog (such as to consolidate searching across CM and non-WCM sites).
16. iMIS Desktop Advanced Install Options: As needed, change what users see and do when they install iMIS Desktop:
□ Force users to install iMIS Desktop to the default path on their local system.
□ Create prompts to guide users during the client install.
□ Prevent or enable users to modify their existing iMIS installation through Control Panel > Add or Remove Programs.
17. Specify ASI license information: Enter the information per your agreement, and click Next.
If you are upgrading from a previous release of iMIS, the current license details are displayed. If you have purchased additional product keys with this release, add the additional license keys here before continuing.
(upgrades) Caution! Ensure that a CASUAL license key is present before continuing, or essential business objects will not be created and will require subsequent repair.
18. Review installation settings: Verify the settings and click Next. The wizard displays setup status as it copies files.
19. (upgrades) iMIS DB Upgrader begins automatically upgrading your database, and it closes on completion.
20. Omnis Serialization Details: Enter your information from your licensing agreement (the serial number is on the yellow card) and click OK.
21. InstallShield Wizard Complete: Review all messages that are displayed on the completion page, take actions as needed, and click Finish.
22. (upgrades) iMIS Database Upgrader: Review the upgrade logs to confirm database upgrade success and any additional post-upgrade needs. Click View Logs and scan the most recent iMISDBUpgrade.log file for the following error message, which indicates a failed database upgrade:
*** UPGRADE PROCESS ENDED WITH ERRORS !!! ***
If you find this error message, your database was not successfully upgraded, so you need to fix the data and upgrade again:
□ To locate the problem, identify which upgrade script failed: Scroll up through the log until you find the header stamp that immediately precedes the error message. Header stamps look like this:
= iMIS x.x.x.x to iMIS x.x.x.x Database Upgrade Driver Script =
□ Fix the data in the current version of the database (it will upgrade from where it stopped)
□ Restart the upgrade: in iMIS Database Upgrader, click Begin Upgrade.
23. (upgrades) Manually re-create any full-text indexes that you dropped (see Preparing all servers and workstations).
24. Reboot the server to ensure that logon handling is properly initialized.
Failure to initialize might result in user passwords being openly displayed (unmasked) during log on.